High performance map editor for business analysts

ABSTRACT

At least one model synchronization map table is built that facilitates navigation between elements of business objects of a business object model and corresponding elements of an extensible markup language (XML) schema definition-based (XSD-based) model. The XSD-based model includes at least one XML schema and is generated from the business object model. The business object model and the XSD-based model are displayed in a dual-view editor. The dual-view editor enables a user to toggle between and independently edit the business object model and the XSD-based model. In response to independent edits made to one of the XSD-based model and the business object model within the dual-view editor, the elements of the business object model are automatically synchronized with the corresponding elements of the XSD-based model using the at least one model synchronization map table.

BACKGROUND

This invention relates to apparatus and methods for implementing abusiness process map editor for business analysts.

Modern business processes are often quite complex, which can make changedifficult. Nevertheless, to maintain profitability and competiveness intoday's marketplace, businesses need to be able to change quickly totake advantage of market opportunities, innovations, expansions,acquisitions, and partnerships with other businesses. To achieve suchchange, businesses need to have a comprehensive understanding of theirinternal business structures, including their internal businessprocesses, rules, data, and transformations. This need for understandingis driving the growth of technologies such as business process modeling(BPM).

Business process modeling (BPM) generally refers to the activity ofrepresenting the processes of a business so that the processes can beanalyzed and improved. BPM is typically performed by business analystsand managers who are seeking to improve process efficiency and quality.The process improvements identified by BPM may or may not require theinvolvement of information technology (IT), although this is often theimpetus for modeling a business process.

To perform BPM within an organization, various tools have beendeveloped. For example, the Websphere Business Modeler map editorprovides a tool for business analysts to define transforms that mapinput data into output data. The Websphere Business Modeler map editorversion 6.2 and older provides a simple map editor with very fewfunctions. These functions are typically inadequate and limit businessusers from creating more complex mappings.

In view of the foregoing, what is needed is a BPM map editor thatprovides a richer set of functions for mapping input data into outputdata. Ideally, such a map editor would be able to leverage thefunctionality already present in IT-based mapping tools which allow morecomplex mappings to be defined. This would also minimize the duplicationof effort associated with developing business-analyst-based tools andIT-based tools separately.

SUMMARY

The invention has been developed in response to the present state of theart and, in particular, in response to the problems and needs in the artthat have not yet been fully solved by currently available systems andmethods. Accordingly, the invention has been developed to providesystems and methods for implementing feature-rich BPM map editors forbusiness analysts. The features and advantages of the invention willbecome more fully apparent from the following description and appendedclaims, or may be learned by practice of the invention as set forthhereinafter.

Consistent with the foregoing, a method for implementing a map editorfor business analysts is disclosed herein. In one embodiment, such amethod includes receiving a business object model including at least onebusiness object. The business object model is transformed into anXSD-based model including at least one XML schema. The XSD-based modelis then fed into an XML mapping infrastructure for model map processing.After processing, the XSD-based model is transformed into a resultingbusiness object model. The resulting business object model may then bedisplayed for use by a business analyst.

A corresponding computer program product and system are also disclosedand claimed herein.

BRIEF DESCRIPTION OF THE DRAWINGS

In order that the advantages of the invention will be readilyunderstood, a more particular description of the invention brieflydescribed above will be rendered by reference to specific embodimentsillustrated in the appended drawings. Understanding that these drawingsdepict only typical embodiments of the invention and are not thereforeto be considered limiting of its scope, the invention will be describedand explained with additional specificity and detail through use of theaccompanying drawings, in which:

FIG. 1 is a high-level block diagram showing one example of a computersystem to implement an improved map editor in accordance with theinvention;

FIG. 2 is a high-level block diagram showing various components of a mapeditor in accordance with the invention;

FIG. 3 is a block diagram showing a transformation between a BOMbusiness object and an XML schema;

FIG. 4 is pseudo code showing possible operation of a map table builderin accordance with the invention;

FIG. 5 is a high-level block diagram showing the operation of thesynchronization engine;

FIG. 6 is a diagram showing one embodiment of a dual-view editordisplaying a business object model; and

FIG. 7 is a diagram showing one embodiment of a dual-view editordisplaying an XSD-based model.

DETAILED DESCRIPTION

It will be readily understood that the components of the presentinvention, as generally described and illustrated in the Figures herein,could be arranged and designed in a wide variety of differentconfigurations. Thus, the following more detailed description of theembodiments of the invention, as represented in the Figures, is notintended to limit the scope of the invention, as claimed, but is merelyrepresentative of certain examples of presently contemplated embodimentsin accordance with the invention. The presently described embodimentswill be best understood by reference to the drawings, wherein like partsare designated by like numerals throughout.

As will be appreciated by one skilled in the art, the present inventionmay be embodied as an apparatus, system, method, or computer programproduct. Furthermore, the present invention may take the form of ahardware embodiment, a software embodiment (including firmware, residentsoftware, microcode, etc.) configured to operate hardware, or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “module” or “system.” Furthermore,the present invention may take the form of a computer-usable storagemedium embodied in any tangible medium of expression havingcomputer-usable program code stored therein.

Any combination of one or more computer-usable or computer-readablestorage medium(s) may be utilized to store the computer program product.The computer-usable or computer-readable storage medium may be, forexample but not limited to, an electronic, magnetic, optical,electromagnetic, infrared, or semiconductor system, apparatus, ordevice. More specific examples (a non-exhaustive list) of thecomputer-readable storage medium may include the following: anelectrical connection having one or more wires, a portable computerdiskette, a hard disk, a random access memory (RAM), a read-only memory(ROM), an erasable programmable read-only memory (EPROM or Flashmemory), an optical fiber, a portable compact disc read-only memory(CDROM), an optical storage device, or a magnetic storage device. In thecontext of this document, a computer-usable or computer-readable storagemedium may be any medium that can contain, store, or transport theprogram for use by or in connection with the instruction executionsystem, apparatus, or device.

Computer program code for carrying out operations of the presentinvention may be written in any combination of one or more programminglanguages, including an object-oriented programming language such asJava™, Smalltalk, C++, or the like, and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. Computer program code for implementing theinvention may also be written in a low-level programming language suchas assembly language.

The present invention may be described below with reference to flowchartillustrations and/or block diagrams of methods, apparatus, systems, andcomputer program products according to embodiments of the invention. Itwill be understood that each block of the flowchart illustrations and/orblock diagrams, and combinations of blocks in the flowchartillustrations and/or block diagrams, may be implemented by computerprogram instructions or code. The computer program instructions may beprovided to a processor of a general-purpose computer, special-purposecomputer, or other programmable data processing apparatus to produce amachine, such that the instructions, which execute via the processor ofthe computer or other programmable data processing apparatus, createmeans for implementing the functions/acts specified in the flowchartand/or block diagram block or blocks.

The computer program instructions may also be stored in acomputer-readable storage medium that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablestorage medium produce an article of manufacture including instructionmeans which implement the function/act specified in the flowchart and/orblock diagram block or blocks. The computer program instructions mayalso be loaded onto a computer or other programmable data processingapparatus to cause a series of operational steps to be performed on thecomputer or other programmable apparatus to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

Referring to FIG. 1, one example of a computer system 100 isillustrated. The computer system 100 is presented to show one example ofan environment where an improved map editor in accordance with theinvention may be implemented. The computer system 100 is presented onlyby way of example and is not intended to be limiting. Indeed, the mapeditor disclosed herein may be implemented on a wide variety ofdifferent computer systems in addition to the computer system 100 shown.The map editor disclosed herein may also potentially be distributedacross multiple computer systems 100.

The computer system 100 includes at least one processor 102 and mayinclude more than one processor. The processor 102 includes one or moreregisters 104 storing data describing the state of the processor andfacilitating execution of software systems. The registers 104 may beinternal to the processor 102 or may be stored in a memory 106. Thememory 106 stores operational and executable data that is operated uponby the processor 102. The memory 106 may be accessed by the processor102 by means of a memory controller 108. The memory 106 may includevolatile memory (e.g., RAM) as well as non-volatile memory (e.g., ROM,EPROM, EEPROM, hard disks, flash memory, etc.).

The processor 102 may be coupled to additional devices supportingexecution of software and interaction with users. For example, theprocessor 102 may be coupled to one or more input devices 110, such as amouse, keyboard, touch screen, microphone, or the like. The processor102 may also be coupled to one or more output devices such as a displaydevice 112, speaker, or the like. The processor 102 may communicate withone or more other computer systems by means of a network 114, such as aLAN, WAN, or the Internet. Communication over the network 114 may befacilitated by a network adapter 116.

Referring to FIG. 2, a high-level block diagram showing one example of asystem 200 for implementing a map editor is illustrated. As previouslymentioned, some business-analyst tools, such as Websphere BusinessModeler map editor version 6.2 and older, provide simple map editorswith very few functions. These functions are typically inadequate andlimit business users from creating more complex mappings. On the otherhand, various IT-based tools, such as the XML map editor from WebsphereIntegration Developer, are complex tools that provide a much richer setof functions for mapping input data into output data. The XML map editorfrom Websphere Integration Developer in particular includes anunderlying XML mapping infrastructure that enables developers to extendand reuse functionalities for mapping.

The systems and methods disclosed herein use an XML mappinginfrastructure, such as that used in Websphere Integration Developer oranother XML mapping product, to produce a map editor suitable forbusiness analysts. This provides several potential advantages: First,the map editor may inherit a much richer set of functions provided bythe XML mapping infrastructure. This in turn enables more complexmappings to be defined. Second, using the same underlying XML mappinginfrastructure to implement both a business-analyst tool and an IT-basedtool may avoid duplication and reduce production costs for both tools.

The problems associated with using an XML mapping infrastructure toimplement a map editor for business analysts, which are solved by thepresent disclosure, include: First, the XML mapping infrastructurepresents input and output data in an undesirable format. In particular,the XML mapping infrastructure is an IT-based tool that presents data inthe form of XML schemas (XSDs). These XML schemas may be inappropriatefor business-oriented users as they may contain unfamiliar terminologyand formatting. To overcome this problem, a processor is provided toconvert XML schemas into a format that is more appropriate for businessanalysts. The details of this processor will be described in more detailhereafter. Second, the XML mapping infrastructure only accepts inputsand outputs described in terms of XML schemas. A business-analyst tool,on the other hand, needs to operate on business objects, such as thoseconforming to the Business Object Model (BOM model)—an IBM proprietaryformat. To utilize the XML mapping infrastructure, these businessobjects are converted into XML schemas. Although converting artifactsfrom one form to another can create undesirable performance impacts,various mechanisms may be employed to minimize these impacts. Thesemechanisms will be discussed in more detail hereafter.

FIG. 2 shows one embodiment of a system 200 for implementing a mapeditor in accordance with the invention. As shown, a map editor 204interfaces with an XML mapping infrastructure 202 and a BO-XSD processor210 to convert artifacts from one form to another. In operation, when aninput or output business object is added to a business process model,the XML mapping infrastructure 202 delegates the task to the map editor204 to locate and load the corresponding XML schema (XSD) for that inputor output. Given the business object (BO) 206, the map editor 204requests a corresponding XML schema 208 from the BO-XSD processor 210.The XML schema 208 is then returned back to the XML mappinginfrastructure 202 for further map model processing. For presentation,the XML mapping infrastructure 202 again requests data from the mapeditor 204 for displaying labels and icons that are appropriate for abusiness analyst. More specifically, given an XML schema 208, the mapeditor 204 retrieves the corresponding business object 206 from theprocessor 210. The map editor 204 then returns the appropriate data backto the XML mapping infrastructure 202 for display.

In selected embodiments, the BO-XSD processor 210 includes four maincomponents: a BO-XSD transformer 212, a BO-XSD map table builder 214, aglobal registry 216, and a synchronization engine 218. The BO-XSDtransformer 212 is configured to transform business objects 206 into XMLschemas 208 and vice versa. FIG. 3 shows one example of a transformationbetween a business object 206 and an XML schema 208. As shown, thebusiness object 206 may include elements 300 that are easy to read andunderstand for typical business analysts, who may not have a backgroundin programming or information technology. The XML schema 208, on theother hand, may be tailored to the programmer or IT professional. Forexample the schema name (i.e., Customersemailaddress) and element names302 (i.e., “Customersname,” “Customersage,” etc.) are not as readableand the business analyst may be unfamiliar with data types such as“string.” The BO-XSD transformer 212 processes the result of thetransformation by identifying and mapping each generated element in theschema to each corresponding element in the business object. The resultis then cached and passed on to the BO-XSD map table builder 214.

Using the cached information received from the BO-XSD transformer 212,the BO-XSD map table builder 214 recursively builds map tables thatenable navigation between elements in the business object andcorresponding elements in the XML schema. FIG. 4 shows one embodiment ofan algorithm (written in pseudocode) for building such a map table. Ingeneral, the algorithm walks through each element in a business object(referred to as a “business item” in the pseudocode) and finds thecorresponding element in the XML schema generated by the BO-XSDtransformer 212. The algorithm stores the relationship between theelements in a mapping table. The algorithm continues this process foreach element in the business object until all correspondingrelationships are found. Among other benefits, this mapping allows auser to easily toggle between a business object model and acorresponding XSD-based model, as will be explained in more detail inassociation with FIGS. 6 and 7.

The map tables produced by the map table builder 214 may be stored in aglobal registry 216, acting as a cache, maintained by the BO-XSDprocessor 210. When the processor 210 receives a request from the mapeditor 204 for an XML schema 208 associated with a business object, theprocessor 210 may initially check the global registry 216 for anexisting XML schema 208. If the desired XML schema 208 is found, theprocessor 210 will return the XML schema 208 instead of invoking theBO-XSD transformer 212 to build a new one. This improves the performanceof the map editor 204 and reduces the need to convert artifacts from oneform to another.

In selected embodiments, the XML schemas stored in the global registry216 are accessible by multiple map editors 204, each of which mayinclude different maps referencing the same business object. In suchembodiments, the processor 210 may keep track of which editors 204 arecurrently referencing the same business object and thus the same XMLschema in the global registry 216. If no editor 204 references aparticular XML schema in the global registry 216, the processor 210 mayderegister the XML schema (e.g., delete the XML schema) to free upmemory. In other embodiments, the processor 210 retains the XML schemain the global registry 216 for a specified amount of time after it is nolonger referenced by any editor 204, or the processor 210 waits forspecific instructions to deregister the XML schema.

In selected embodiments, the generated XML schemas and mappinginformation are used not only by the map editor 204, but also by asimulation framework (not shown). The simulation framework may use themapping information from the BO-XSD map table builder 214 to populatedata in XML documents generated from the XML schemas. To perform asimulation, a simulation global registry (not shown) containing thepopulated XML documents may be created. In certain embodiments, thesimulation global registry is cleaned up after the simulation isperformed.

Referring to FIG. 5, as mentioned above, the BO-XSD processor 210 mayalso include a synchronization engine 218 to keep business objects andcorresponding XML schemas synchronized. When modeling a business processin the map editor 204, a business object may be modified at any time.The synchronization engine 218 ensures that the XML schemas in theglobal registry 216 are up-to-date and in sync with the correspondingbusiness objects. In selected embodiments, the XML schemas are updatedincrementally to improve performance. Such incremental updates may onlyupdate the parts of the XML schema that are affected by changes to abusiness object, as opposed to regenerating the XML schema in itsentirety. In other embodiments, an XML schema is regenerated in itsentirety each time any part of a corresponding business object changes,or if enough of the corresponding business object has changed to warranta complete regeneration.

In selected embodiments, the synchronization engine 218 is registered asan adapter of a business object model. This will enable thesynchronization engine 218 to be notified whenever a business object inthe business object model changes (as indicated by the arrow 400). Upondetecting such a change, the synchronization engine 218 may determinewhether a full or incremental update is needed for the corresponding XMLschema. The synchronization engine 218 may then invoke the BO-XSDtransformer 212 to make the change to the corresponding XML schema (asindicated by the arrow 402) and update the global registry 216 toreflect the change (as indicated by the arrow 404). The synchronizationengine 218 may also notify the map editor 204 of the change (asindicated by the arrow 406) so that the editor 204 can refresh thepresentation of the business object and other parts of the businessmodel that may have changed.

Referring to FIGS. 6 and 7, in selected embodiments, the operation ofthe BO-XSD processor 210 enables the creation of a dual-view editor 600.This dual-view editor 600 may enable a user to toggle between a view ofthe business object model and the XSD-based model. FIG. 6 shows oneexample of the dual-view editor 600 displaying a business object model.This view would be appropriate for non-technical business users. FIG. 7shows one example of the dual-view editor 600 displaying an XSD-basedmodel associated with the business object model. This view would beappropriate for technical personnel, such as IT professionals oradvanced users. A button 602 may be provided in either view to allow auser to toggle between the different views.

In selected embodiments, the dual-view editor 600 allows editing ofeither the business object model or the XSD-based model in theirrespective views. When changes are made to the business object model,the BO-XSD processor 210 makes corresponding changes to the XSD-basedmodel. Similarly, when changes are made to the XSD-based model, theBO-XSD processor 210 makes corresponding changes to the business objectmodel. In this way, the BO-XSD processor 210 keeps the two modelssynchronized.

To view the business object model in the map editor 204, the map editor204 may retrieve the corresponding business object for each XML schemain the model from the BO-XSD processor 210. Using the returned businessobjects, the map editor 204 may then display the data and labels thatare appropriate for business users. To view the XML schema model in themap editor 204, the editor 204 is effectively turned into an XML mapeditor 204. In such a case, the editor 204 delegates the displaying taskback to XML mapping infrastructure 202.

The blocks illustrated in FIGS. 1, 2, and 5 may be implemented in theform of one or more modules. Such modules may be implemented inhardware, software or firmware executable on hardware, or a combinationthereof. The modules are presented only by way of example and are notintended to be limiting. Indeed, alternative embodiments may includemore or fewer modules than those illustrated. It should also berecognized that, in some embodiments, the functionality of some modulesmay be broken into multiple modules or, conversely, the functionality ofseveral modules may be combined into a single module or fewer modules.It should also be recognized that the modules are not necessarilyimplemented in the locations where they are illustrated. For example,some functionality shown in the BO-XSD processor 210 may be implementedin other locations or as stand-alone modules. Thus, the location of themodules is presented only by way of example and is not intended to belimiting.

The flowcharts and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer-usable media according to variousembodiments of the present invention. In this regard, each block in theflowcharts or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the Figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. Some blocks may bedeleted or other blocks may be added depending on the functionalityinvolved. It will also be noted that each block of the block diagramsand/or flowchart illustrations, and combinations of blocks in the blockdiagrams and/or flowchart illustrations, may be implemented by specialpurpose hardware-based systems that perform the specified functions oracts, or combinations of special purpose hardware and computerinstructions.

What is claimed is:
 1. A computer-implemented method, comprising:building at least one model synchronization map table that facilitatesnavigation between elements of business objects of a business objectmodel and corresponding elements of an extensible markup language (XML)schema definition-based (XSD-based) model comprising at least one XMLschema and generated from the business object model; displaying thebusiness object model and the XSD-based model in a dual-view editor, thedual-view editor enabling a user to toggle between and independentlyedit the business object model and the XSD-based model; automaticallysynchronizing, using the at least one model synchronization map table,the elements of the business objects of the business object model withthe corresponding elements of the XSD-based model in response toindependent edits made to one of the XSD-based model and the businessobject model within the dual-view editor; registering the automatedsynchronization of the elements of the business objects of the businessobject model with the corresponding elements of the XSD-based model asan adapter of the business object model; receiving, responsive to anindependent edit made to the business object model within the dual-vieweditor, a notification from the adapter of the business object model;invoking an incremental transformation of the corresponding XML schema;refreshing the displayed XSD-based model to reflect the incrementaltransformation of the corresponding XML schema; and updating a globalregistry with the incremental transformation of the corresponding XMLschema.
 2. The computer-implemented method of claim 1, where displayingthe business object model and the XSD-based model in the dual-vieweditor comprises delegating the displaying of the business object modeland the XSD-based model in the dual-view editor to an XML mappinginfrastructure.
 3. The computer-implemented method of claim 1, whereautomatically synchronizing, using the at least one modelsynchronization map table, the elements of the business objects of thebusiness object model with the corresponding elements of the XSD-basedmodel in response to the independent edits made to the one of theXSD-based model and the business object model within the dual-vieweditor comprises: incrementally synchronizing the elements of thebusiness objects of the business object model with the correspondingelements of the XSD-based model in response to each independent editmade to the one of the XSD-based model and the business object modelwithin the dual-view editor.
 4. A system, comprising: a memory; and aprocessor programmed to: build, within the memory, at least one modelsynchronization map table that facilitates navigation between elementsof business objects of a business object model and correspondingelements of an extensible markup language (XML) schema definition-based(XSD-based) model comprising at least one XML schema and generated fromthe business object model; display the business object model and theXSD-based model in a dual-view editor, the dual-view editor enabling auser to toggle between and independently edit the business object modeland the XSD-based model; automatically synchronize, using the at leastone model synchronization map table, the elements of the businessobjects of the business object model with the corresponding elements ofthe XSD-based model in response to independent edits made to one of theXSD-based model and the business object model within the dual-vieweditor; register the automated synchronization of the elements of thebusiness objects of the business object model with the correspondingelements of the XSD-based model as an adapter of the business objectmodel; receive, responsive to an independent edit made to the businessobject model within the dual-view editor, a notification from theadapter of the business object model; invoke an incrementaltransformation of the corresponding XML schema; refresh the displayedXSD-based model to reflect the incremental transformation of thecorresponding XML schema; and update a global registry with theincremental transformation of the corresponding XML schema.
 5. Thesystem of claim 4, where, in being programmed to display the businessobject model and the XSD-based model in the dual-view editor, theprocessor is programmed to delegate the displaying of the businessobject model and the XSD-based model in the dual-view editor to an XMLmapping infrastructure.
 6. The system of claim 4, where, in beingprogrammed to automatically synchronize, using the at least one modelsynchronization map table, the elements of the business objects of thebusiness object model with the corresponding elements of the XSD-basedmodel in response to the independent edits made to the one of theXSD-based model and the business object model within the dual-vieweditor, the processor is programmed to: incrementally synchronize theelements of the business objects of the business object model with thecorresponding elements of the XSD-based model in response to eachindependent edit made to the one of the XSD-based model and the businessobject model within the dual-view editor.
 7. A computer program productcomprising a computer-usable storage medium having computer-usableprogram code embodied therein, where the computer-usable storage mediumis not a transitory signal per se and the computer-usable program codewhen executed on a computer causes the computer to: build at least onemodel synchronization map table that facilitates navigation betweenelements of business objects of a business object model andcorresponding elements of an extensible markup language (XML) schemadefinition-based (XSD-based) model comprising at least one XML schemaand generated from the business object model; display the businessobject model and the XSD-based model in a dual-view editor, thedual-view editor enabling a user to toggle between and independentlyedit the business object model and the XSD-based model; automaticallysynchronize, using the at least one model synchronization map table, theelements of the business objects of the business object model with thecorresponding elements of the XSD-based model in response to independentedits made to one of the XSD-based model and the business object modelwithin the dual-view editor; register the automated synchronization ofthe elements of the business objects of the business object model withthe corresponding elements of the XSD-based model as an adapter of thebusiness object model; receive, responsive to an independent edit madeto the business object model within the dual-view editor, a notificationfrom the adapter of the business object model; invoke an incrementaltransformation of the corresponding XML schema; refresh the displayedXSD-based model to reflect the incremental transformation of thecorresponding XML schema; and update a global registry with theincremental transformation of the corresponding XML schema.
 8. Thecomputer program product of claim 7, where, in causing the computer todisplay the business object model and the XSD-based model in thedual-view editor, the computer-usable program code when executed on thecomputer causes the computer to delegate the displaying of the businessobject model and the XSD-based model in the dual-view editor to an XMLmapping infrastructure.
 9. The computer program product of claim 7,where, in causing the computer to automatically synchronize, using theat least one model synchronization map table, the elements of thebusiness objects of the business object model with the correspondingelements of the XSD-based model in response to the independent editsmade to the one of the XSD-based model and the business object modelwithin the dual-view editor, the computer-usable program code whenexecuted on the computer causes the computer to: incrementallysynchronize the elements of the business objects of the business objectmodel with the corresponding elements of the XSD-based model in responseto each independent edit made to the one of the XSD-based model and thebusiness object model within the dual-view editor.